TDD-RLAN wireless telecommunication system with RAN IP gateway and methods

ABSTRACT

The present invention provides for a Time Division Duplex - Radio Local Area Network (TDD-RLAN) which includes a Radio Access Network Internet Protocol (RAN IP) gateway that enables connectivity to the public Internet. The system may serve as a stand-alone system or be incorporated into a UMTS used with conventional Core Network, particularly for tracking and implementing AAA functions in the Core Network.

CROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims priority from U.S. ProvisionalApplication No. 60/367,949, filed Mar. 26, 2002; U.S. ProvisionalApplication No. 60/367,975, filed Mar. 26, 2002; U.S. ProvisionalApplication No. 60/367,946, filed Mar. 26, 2002; U.S. ProvisionalApplication No. 60/367,945, filed Mar. 26, 2002; U.S. ProvisionalApplication No. 60/367,950, filed Mar. 26, 2002; and U.S. ProvisionalApplication No. 60/367,948, filed Mar. 26, 2002, which are incorporatedherein by reference as if fully set forth.

FIELD OF INVENTION

[0002] The present invention relates to wireless telecommunicationsystems and in particular to Time Division Duplex - Radio Local AreaNetwork (TDD-RLAN) Code Division Multiple Access (CDMA) systems andconnection and communication of such systems with the Internet.

BACKGROUND

[0003] Wireless telecommunication systems are well known in the art.Wireless systems require an available bandwidth in which to operate.Typically, the permission to use a portion of the available spectrum forwireless communication for a particular geographic region is obtainedfrom an appropriate governmental unit of the physical territory in whichthe wireless communications are to be conducted. In order to makeefficient use of limited spectrum available for operation of a wirelesstelecommunication system, Code Division Multiple Access (CDMA) systemshave been developed which include Time Division Duplex (TDD) modes whichprovide a very flexible framework for providing concurrent wirelesscommunication services. Supported wireless communication services can beany of a variety of types including voice, fax, and a host of other datacommunication services.

[0004] In order to provide global connectivity for CDMA systems,standards have been developed and are being implemented. One currentstandard in widespread use is known as Global System for MobileTelecommunications (GSM). This was followed by the so-called SecondGeneration mobile radio system standards (2G) and its revision (2.5G).Each one of these standards sought to improve upon the prior standardwith additional features and enhancements. In January 1998, the EuropeanTelecommunications Standard Institute - Special Mobile Group (ETSI SMG)agreed on a radio access scheme for Third Generation Radio Systemscalled Universal Mobile Telecommunications Systems (UMTS). To furtherimplement the UMTS standard, the Third Generation Partnership Project(3GPP) was formed in December 1998. 3GPP continues to work on a commonthird generational mobile radio standard.

[0005] A typical UMTS system architecture in accordance with current3GPP specifications is depicted in FIGS. 1 and 2. The UMTS networkarchitecture includes a Core Network (CN) interconnected with a UMTSTerrestrial Radio Access Network (UTRAN) via an interface known as IUwhich is defined in detail in the current publicly available 3GPPspecification documents.

[0006] The UTRAN is configured to provide wireless telecommunicationservices to users through User Equipments (UEs) via a radio interfaceknown as UU. The UTRAN has base stations, known as Node Bs in 3GPP,which collectively provide for the geographic coverage for wirelesscommunications with UEs. In the UTRAN, groups of one or more Node Bs areconnected to a Radio Network Controller (RNC) via an interface known asIub in 3GPP. The UTRAN may have several groups of Node Bs connected todifferent RNCs, two are shown in the example depicted in FIG. 1. Wheremore than one RNC is provided in a UTRAN, inter-RNC communication isperformed via an Iur interface.

[0007] A UE will generally have a Home UMTS Network (HN) with which itis registered and through which billing and other functions areprocessed. By standardizing the Uu interface, UEs are able tocommunicate via different UMTS networks that, for example, servedifferent geographic areas. In such case the other network is generallyreferred to as a Foreign Network (FN).

[0008] Under current 3GPP specifications, the Core Network of a UE's HNserves to coordinate and process the functions of Authentication,Authorization and Accounting (AAA functions). When a UE travels beyondits Home UMTS Network, the HN's Core Network facilitates the UE's use ofa Foreign Network by being able to coordinate the AAA functions so thatthe FN will permit the UE to conduct communications. To assist inimplementing this activity, the Core Network includes a Home LocationRegister (HLR) which tracks the UEs for which it is the HN and a VisitorLocation Register (VLR). A Home Service Server (HSS) is provided inconjunction with the HLR to process the AAA functions.

[0009] Under current 3GPP specifications, the Core Network, but not theUTRAN, is configured with connectivity to external systems such asPublic Land Mobile Networks (PLMN), Public Switch Telephone Networks(PSTN), Integrated Services Digital Network (ISDN) and other Real Time(RT) services via an RT service interface. A Core Network will alsosupport Non-Real Time services with the Internet. External connectivityof the Core Network to other systems, enables users using UEs tocommunicate via their Home UMTS Network, beyond the area served by theHN's UTRAN. Visiting UEs can likewise communicate via a visited UMTSNetwork, beyond the area served by the visited UMTS's UTRAN.

[0010] Under current 3GPP specifications, the Core Network provides RTservice external connectivity via a Gateway Mobile Switching Center(GMSC). The Core Network provides NRT service, known as General PacketRadio Service (GPRS), external connectivity via a Gateway GPRS SupportNode (GGSN). In this context, a particular NRT service may actuallyappear to a user to be a real time communication due to thecommunication speed and associated buffering of the TDD data packetsforming the communication. One example of this is voice communicationvia the Internet which can appear to the user as a normal telephone callconducted by a switching network, but is actually being conducted usingan Internet Protocol (IP) connection which provides Packet data Service.

[0011] A standard interface known as GI is generally used between a CN'sGGSN and the Internet. The GI interface can be used with Mobile InternetProtocols, such as Mobile IP v4 or Mobile IP v6 as specified by theInternet Engineering Task Force (IETF).

[0012] Under current 3GPP specifications, to provide support for both RTand NRT services from external sources for radio linked UEs in a 3GPPsystem, the UTRAN must properly interface with the CN which is thefunction of the Iu interface. To do this, the Core Network includes aMobile Switching Centre (MSC) that is coupled to the GMSC and a ServingGPRS Support Node (SGSN) that is coupled to the GGSN. Both are coupledwith the HRL and the MSC is usually combined with the Visitor LocationRegister (VLR).

[0013] The Iu interface is divided between an interface for CircuitSwitched communications (Iu-CS) and an interface for packet data viaPacket Switched communications (lu-PS). The MSC is connected to the RNCsof the UTRAN via the Iu-CS interface. The Serving GPRS Support Node(SGSN) is coupled to the UTRAN's RNCs via the Iu-PS interface for PacketData Services.

[0014] The HLR/HSS is typically interfaced with the CS side of the CoreNetwork, MSC and GMSC via an interface known as Gr which supports AAAfunctions through a Mobile Application Part (MAP) Protocol. The SGSN andthe GGSN of the CN are connected using interfaces known as Gn and Gp.

[0015] Common to 3GPP systems and other systems which utilize TDD-CDMAtelecommunications, such as some GSM systems, is the aforementioneddivision of connectivity between the radio network and the Core Network.In general, the radio network, i.e. the UTRAN in 3GPP, communicates viaa wireless interface with UEs and the Core Network communicates withexternal systems via RT and NRT service connections. Applicants haverecognized this standardized type of architecture is most likely theresult of the processing of the AAA functions in the Core Network.However, applicants have further recognized that even if the AAAfunctions are to be maintained in the Core Network, significantadvantages and benefits can be obtained by providing direct connectivityfrom a TDD-CDMA radio network to the Internet.

[0016] In particular, Applicants have recognized that the existingseparation of functions of the Iu interface defined in 3GPP for CircuitSwitched (CS) communications used with Real Time services (Iu-CSinterface) and defined in 3GPP for Packet Switch (PS) service used withNon-Real Time services (Iu-PS interface), enables one to easily providean IP Gateway in the UTRAN for enabling the UTRAN to direct connectivityto the Internet bypassing use of a Core Network for this function.Moreover, as a result, Applicants have recognized that by permittingdirect access to the Internet from the UTRAN, a Radio Local Area Networkis defined that can provide significant benefits and advantages for usewith or without a Core Network.

[0017] Further detail of a typical 3GPP system is illustrated in FIG. 3.The UTRAN segment of a conventional UMTS architecture is split it intotwo traffic planes known as the C- and U- planes. The C-plane carriescontrol (signaling) traffic, and the U-plane transports user data. Theover-the-air segment of the UTRAN involves two interfaces: the Uuinterface between UE and Node B, and the Iub interface between the NodeB and RNC. As noted above, the back-end interface between the RNC andcore network is referred to as the Iu interface, split into the Iu-CSfor the circuit-switched connection into the MSC, and the Iu-PS for thepacket-switched connection into the SGSN.

[0018] The most significant signaling protocol on the over-the-airsegment of the UTRAN is Radio Resource Control (RRC). RRC manages theallocation of connections, radio bearers and physical resources over theair interface. In 3GPP, RRC signaling is carried over the Radio LinkControl (RLC) and Medium Access Control (MAC) UMTS protocols between theUE and RNC. Overall, the RNC is responsible for theallocation/de-allocation of radio resources, and for the management ofkey procedures such as connection management, paging and handover. Overthe Iub interface, RRC/RLC/MAC messaging is typically carried on aTransport Layer via Asynchronous Transfer Mode (ATM), using the ATMAdaptation Layer Type 5 (AAL5) protocol over the ATM physical layer withintermediary protocols, such as Service Specific Co-ordination Function(SSCF) and the Service Specific Connection Oriented Protocol SSCOP,being used above AAL5.

[0019] U-plane data (e.g. speech, packet data, circuit-switched data)uses the RLC/MAC layers for reliable transfer over the air interface(between UE and RNC). Over the Iub segment, this data flow (userdata/RLC/MAC) occurs over UMTS-specified frame protocols using the ATMAdaptation Layer Type 2 (AAL2) protocol over the ATM physical layerrunning (AAL2/ATM).

[0020] The Iu interface carries the Radio Access Network ApplicationPart (RANAP) protocol. RANAP triggers various radio resource managementand mobility procedures to occur over the UTRAN, and is also responsiblefor managing the establishment/release of terrestrial bearer connectionsbetween the RNC and SGSN/MSC. RANAP is carried over AAL5/ATM, withintermediary Signaling System 7 (SS7) protocols, such as SignalingConnection Control Part, Message Transfer Part (SCCP/MTP) on top of SSCFand the Service Specific Connection Oriented Protocol (SSCOP), beingused above AAL5. Internet Protocol is typically used over AAL5/ATM forthe Iu-PS interface so that the intermediate Stream Control TransmissionProtocol (SCTP) is then used over IP. Where multiple RNCs exist in aUTRAN which have an Iur interface, IP is also commonly used over ATM andintermediate protocols include SSCP, SCTP and the Message Transfer Partlevel 3 SCCP adaptation layer of SS7 (M3UA) that have been developed byIETF.

[0021] For the U-Plane, between the UTRAN and the CN, circuit-switchedvoice/data traffic typically flows over AAL5/ATM, via the Iu-CSinterface, between the RNC and MSC. Packet-switched data is carried overthe Iu-PS interface between the RNC and SGSN, using the GPRS TunnelingProtocol (GTP) running over the User Data Protocol for the InternetProtocol (UDP/IP) over AAL5/ATM.

[0022] Applicants have recognized that this architecture can be improvedupon in connection with providing direct IP connectivity for the UTRAN.

SUMMARY

[0023] The present invention provides for a Time Division Duplex - RadioLocal Area Network (TDD-RLAN) which includes a Radio Access NetworkInternet Protocol (RAN IP) gateway that enables connectivity to thepublic Internet. The system may serve as a stand-alone system or beincorporated into a UMTS used with conventional Core Network,particularly for tracking and implementing AAA functions in the CoreNetwork.

[0024] The RLAN provides concurrent wireless telecommunication servicesfor a plurality of user equipments (UEs) between UEs and/or theInternet. The RLAN includes at least one base station that has atransceiver for conducting time division duplex (TDD) code divisionmultiple access (CDMA) wireless communications with UEs in a selectedgeographic region. The RLAN also has at least one controller that iscoupled with a group of base stations, which includes the base station.The controller controls the communications of the group of basestations. A novel Radio Access Network Internet Protocol (RAN IP)Gateway (RIP GW) is coupled with the controller. The RAN IP Gateway hasa Gateway General Packet Radio Service (GPRS) Support Node (GGSN) withaccess router functions for connection with the Internet.

[0025] The RLAN can include a plurality of base stations, each having atransceiver configured with a Uu interface for conducting time divisionduplex (TDD) wideband code division multiple access (W-CDMA) wirelesscommunications with UEs in a selected geographic region. The RLAN canalso include a plurality of controllers that are each coupled with agroup of base stations.

[0026] Preferably, the RAN IP Gateway has a Serving GPRS Support Node(SGSN) that is coupled with one or more controllers in the RLAN.Preferably, the controllers are Radio Network Controller (RNCs) inaccordance with 3GPP specification. Preferably, the RNCs are coupledwith the base stations using a stacked, layered protocol connectionhaving a lower transport layer configured to use Internet Protocol (IP).Where the RLAN has multiple RNCs, the RNCs are preferably coupled toeach other using a stacked, layered protocol connection having a lowertransport layer configured to use Internet Protocol (IP)

[0027] Methods of mobility management using a radio local area network(RLAN) are disclosed for providing concurrent wireless telecommunicationservices for a plurality of UEs where an associated core network (CN)supports Authentication, Authorization and Accounting (AAA) functions ofUEs. A RLAN conducts TDD-CDMA wireless communications with UEs in a RLANservice region. The RLAN has a RAN IP Gateway that has a GPRS connectionwith the Internet and is configured to communicate AAA functioninformation to the associated CN.

[0028] In one method, a wireless connection is established between afirst UE within the RLAN service region and a second UE outside of theRLAN service region for conducting a communication of user data. AAAfunctions for said communication between said first and second UEs areconducted using the Core Network. The GPRS connection with the Internetis used for transporting user data of the communication between thefirst and second UEs. The method may include continuing the wirelesscommunication between the first and second UEs as the second UE movesfrom outside to within the RLAN service region, where use of the GPRSconnection with the Internet for transporting user data is discontinued.The method can further include continuing the wireless communicationbetween the first and second UEs as either the first or second UE movesfrom within to outside the RLAN service region by resuming use of theGPRS connection with the Internet for transporting user data.

[0029] In another method, a wireless connection is established betweenfirst and second UEs within the RLAN service region for conducting acommunication of user data. AAA functions for the communication betweenthe first and second UEs are conducted using the Core Network. Thewireless communication between the first and second UEs is continued aseither the first or second UE moves from within to outside the RLANservice region by using the GPRS connection with the Internet fortransporting user data of the continued communication.

[0030] A further method of mobility management is provided where theassociated CN supports AAA functions of home UEs and the GPRS connectionof the RAN IP Gateway is configured to tunnel AAA function informationthrough the Internet to the Core Network. A wireless connection isestablished between a home UE and a second UE for conducting acommunication of user data. AAA functions for the communication areconducted using the Core Network by using the GPRS connection with theInternet to tunnel AAA function information through the Internet to theCore Network.

[0031] This method may be used where the wireless connection isestablished when either the home UE or the second UE is within oroutside the RLAN service region. Where one is within and the other isoutside of the RLAN service region, the GPRS connection with theInternet is used for transporting user data of the communication betweenthe home and second UEs.

[0032] This method may further include continuing the wirelesscommunication between the home and second UEs as one moves such thatboth are outside or both are within the RLAN service region, where theuse of said General Packet Radio Service (GPRS) connection with theInternet for transporting user data is discontinued. The method mayfurther include continuing the wireless communication between the homeand second UEs as either the home or second UE moves so that one iswithin and the other is outside the RLAN service region by using theGPRS connection with the Internet for transporting user data for thecontinued communication.

[0033] In one aspect of the invention, the RLAN has as control means oneor more U-Plane and C-Plane Servers coupled with base stations. TheU-Plane Server(s) are configured to control user data flow of basestation communications. The C-Plane Server(s) are configured to controlsignaling for base stations communication. Preferably, the RAN IPGateway has a SGSN that is coupled with the U-plane Servers and at leastone C-Plane Server. Preferably, the U-Plane Servers and C-Plane Serversare coupled with each other, the base stations, and the RAN IP Gatewayusing stacked, layered protocol connections having a lower transportlayer configured to use Internet Protocol (IP).

[0034] Optionally, a Voice Gateway having a Pulse Code Modulation (PCM)port for external connection may be provided for the RLAN. The VoiceGateway is preferably coupled with a U-plane and a C-Plane Server (or anRNC where RNCs are used) using stacked, layered protocol connectionshaving a lower transport layer configured to use Internet Protocol (IP).

[0035] In another aspect of the invention, the RLAN has one or moreRadio Network Controllers (RNCs) coupled with base stations and a RAN IPGateway to which at least one RNC is coupled via an Iu-PS interfaceusing a stacked, layered protocol connection having a lower transportlayer configured to use Internet Protocol (IP). Preferably, the RNCs arecoupled the base stations and each other using stacked, layered protocolconnections having a lower transport layer configured to use InternetProtocol (IP). Preferably, each base station has a transceiverconfigured with a Uu interface for conducting time division duplex (TDD)wideband code division multiple access (W-CDMA) wireless communicationswith UEs in a selected geographic region and the RAN IP Gateway has aSGSN that is coupled with the RNCs.

[0036] In another aspect of the invention, the RLAN supports voicecommunications over IP and has a RAN IP Gateway having a GGSN forconnection with the Internet that passes compressed voice data. The RLANis preferably connected to the Internet via an internet service provider(ISP) that has a voice gateway that converts compressed voice data andPulse Code Modulation (PCM) signaling using a known compressionprotocol, which may or may not be the type of voice compression dataused by UEs conducting wireless communications with the RLAN.

[0037] Where the UEs use one compression protocol and the RLAN isconnected with the Internet via an ISP having a voice gateway thatconverts compressed voice data and PCM signaling using a differentcompression protocol, the RLAN includes a voice data converter forconverting between compressed voice data of the two differentcompression protocols. Preferably, the RAN IP Gateway includes the voicedata converter which is, for example, configured to covert between AMRcompressed voice data and G.729 compressed voice data. The RLAN may beconfigured with U-Plane and C-Plane Servers or RNCs, but preferably allcomponent interfaces within the RLAN use stacked, layered protocolconnections having a lower transport layer configured to use InternetProtocol (IP).

[0038] The invention further provides a telecommunication network havingone or more radio network for providing concurrent wirelesstelecommunication services for a plurality of UEs and an associated CNfor supporting AAA functions of UEs for which the telecommunicationnetwork is a Home Network. One or more of the radio networks is a RLANhaving a RAN IP Gateway that has a GGSN configured with a GI interfacefor connection with the Internet and is configured to communicate AAAfunction information to the CN. Preferably, the RLANs each have one ormore base stations that have a transceiver for conducting TDD-CDMAwireless communications with UEs in a selected geographic region.Preferably, the RLANs have controllers coupled with the base stations.Preferably, the RLANs' RAN IP Gateways have a SGSN that is coupled withthe respective controllers.

[0039] The RLAN may be configured without a direct CN connection wherethe RAN IP Gateway is configured for communication of AAA functioninformation with the CN by tunneling data through an Internetconnection. Alternatively, the RAN IP Gateway has a coupling with the CNfor communication of AAA function information with the CN via a limitedconnection, such as a Radius/Diameter or MAP supporting connection or aconventional Iu-CS interface, or a full conventional Iu interface.

[0040] Preferably, the RAN IP Gateways have GGSNs configured forconnection with the Internet via a GI interface. For mobile support, theGI interface is preferably configured with Mobile IP v4 or Mobile IP v6.

[0041] Other objects and advantages of the present invention will beapparent to those skilled in the art from the following detaileddescription and the drawings.

BRIEF DESCRIPTION OF THE DRAWING(S)

[0042]FIG. 1 is a graphic illustration of a conventional UMTS network inaccordance with current 3GPP specification.

[0043]FIG. 2 is a block diagram showing various components andinterfaces of the network illustrated in FIG. 1.

[0044]FIG. 3 is a schematic diagram of the conventional networkillustrated in FIGS. 1 and 2 indicating layered stacked protocols of thevarious component interfaces in both signaling and user data planes.

[0045]FIG. 4 is a graphic illustration of a UMTS network including aRLAN with a direct Internet link in accordance with the teachings of thepresent invention.

[0046]FIG. 5 is a block diagram showing various components of thenetwork shown in FIG. 4.

[0047]FIG. 6 is a block diagram showing a variation of the network wherethe RLAN has no direct connection with the UMTS Core Network.

[0048]FIG. 7 is a schematic illustration of signaling data flow in theUMTS network illustrated in FIG. 6.

[0049]FIG. 8 is a graphic illustration of a second variation of the UMTSnetwork illustrated in FIG. 4 wherein the RLAN has a first type oflimited connection with the UMTS Core Network.

[0050]FIG. 9 is a graphic illustration of a second variation of the UMTSnetwork illustrated in FIG. 4 wherein the RLAN has a second type oflimited connection with the UMTS Core Network.

[0051]FIGS. 10A and 10B illustrate two variations of IP packet data flowfor the networks shown in FIGS. 4, 8 and 9 wherein Mobile IP v4 protocolis implemented by the RLAN.

[0052]FIGS. 11A and 11B illustrate two variations of IP packet data flowfor the networks shown in FIGS. 4, 8 and 9 wherein Mobile IP v6 protocolis implemented by the RLAN.

[0053]FIG. 12 is a schematic illustration of preferred signaling planeand user plane interfaces within a RLAN made in accordance with theteachings of the present invention.

[0054]FIG. 13 is a schematic illustration of a RLAN having a singleRadio Network Controller in accordance with the teachings of the presentinvention.

[0055]FIG. 14 is a schematic illustration of a RLAN having multipleRadio Network Controllers made in accordance with the teachings of thepresent invention.

[0056]FIG. 15 is an illustrated diagram of an alternate configuration ofan RLAN having separate servers for user data and control signals andalso an optional voice gateway made in accordance with the teachings ofthe present invention.

[0057]FIG. 16 is a block diagram of components of the RLAN illustratedin FIG. 15.

[0058]FIG. 17 is a schematic diagram illustrating a preferred protocolstack for the control plane interfaces of a RLAN made in accordance withthe teachings of the present invention.

[0059]FIG. 18 is a schematic diagram illustrating a preferred protocolstack for the user plane interfaces of a RLAN made in accordance withthe teachings of the present invention.

[0060]FIGS. 19, 20 and 21 are schematic diagrams illustrating threevariations of interface protocol stacks in the user plane for supportingvoice communication between a UE having a wireless connection with anRLAN and an ISP connected to the RLAN which has a voice gateway.

[0061]FIG. 22 is a schematic diagram illustrating a variation ofinterface protocol stacks in the control plane for supporting voicecommunication between a UE having a wireless connection with an RLAN andan ISP connected to the RLAN which has a voice gateway. TABLE OFACRONYMS 2 G Second Generation 2.5 G Second Generation Revision 3GPPThird Generation Partnership Project AAA functions Authentication,Authorization and Accounting functions AAL2 ATM Adaptation Layer Type 2AAL5 ATM Adaptation Layer Type 5 AMR A type of voice data compressionATM Asynchronous Transfer Mode CDMA Code Division Multiple Access CNCore Network CODECs Coder/Decoders C-RNSs Control Radio NetworkSubsystems CS Circuit Switched ETSI European Telecommunications StandardInstitute ETSI SMG ETSI - Special Mobile Group FA Forwarding Address FNForeign Network G.729 A type of voice data compression GGSN Gateway GPRSSupport Node GMM GPRS Mobility Management GMSC Gateway Mobile SwitchingCenter GPRS General Packet Radio Service GSM Global System for MobileTele- communications GTP GPRS Tunneling Protocol GW Gateway H.323/SIPH.323 Format for a Session Initiated Protocol HLR Home Location RegisterHN Home Network HSS Home Service Server IP Internet Protocol ISDNIntegrated Services Digital Network ISP Internet Service Provider Iu-CSIu sub Interface for Circuit Switched service Iu-PS Iu sub Interface forPacket Switched service IWU Inter Working Unit M3UA Message TransferPart Level 3 SCCP SS7 Adaptation Layer MAC Medium Access Control MAPMobile Application Part MSC Mobile Switching Centre NRT Non-Real TimePCM Pulse Code Modulation PLMN Public Land Mobile Network PS PacketSwitched PSTN Public Switch Telephone Network RANAP Radio Access NetworkApplication Part RAN IP Radio Access Network Internet Protocol RIP GWRAN IP Gateway RLAN Radio Local Area Network RLC Radio Link Control RNCRadio Network Controller RRC Radio Resource Control RT Real TimeSCCP/MTP Signaling Connection Control Part, Message Transfer Part SGSNServing GPRS Support Node SCTP Stream Control Transmission Protocol SMSession Management SMS Short Message Service S-RNS Serving Radio NetworkSubsystems SS7 Signaling System 7 SSCF Service Specific CoordinationFunction SSCOP Service Specific Connection Oriented Protocol TDD TimeDivision Duplex UDP/IP User Data Protocol for the Internet Protocol UEUser Equipment UMTS Universal Mobile Telecommunications System UTRANUMTS Terrestrial Radio Access Network VLR Visitor Location Register

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

[0062] With reference to FIG. 4, there is shown a modified UniversalMobile Terrestrial System (UMTS) network having a Radio Local AreaNetwork (RLAN) with a direct Internet connection. As shown in FIG. 5,the RLAN employs base stations to communicate via a wireless radiointerface with the various types of User Equipments (UEs). Preferablythe base stations are of the type specified in 3GPP as node Bs. A radiocontroller is coupled to the base stations to control the wirelessinterface. Preferably the radio controller is a Radio Network Controller(RNC) made in accordance with 3GPP specification. Various combinationsof Node Bs and RNCs may be employed as used in a conventional 3GPPUTRAN. Collectively, the geographic ranges of the wirelesscommunications conducted with the base stations of the RLAN defines theRLAN's service coverage area.

[0063] Unlike a conventional UTRAN, the RLAN of the present inventionincludes a Radio Access Network Internet Protocol (RAN IP) gateway whichprovides connectivity for the RLAN outside its serice coverage area,i.e. the geographic area served by the wireless communication with itsbase stations. As illustrated in FIGS. 4 and 5, the RAN IP gateway has adirect Internet connection and may have the standard direct UMTS networkconnection through an Iu interface with an associated Core Network.Alternatively, as illustrated in FIG. 6, the direct interface between anassociated Core Network and the RAN IP gateway may be omitted so thatthe RAN IP Gateway can have only a direct connection with the Internet.In such case, as illustrated in FIG. 7, the RLAN of the presentinvention may still form a part of a UMTS by the tunneling of controland AAA function information to a Core Network which serves as its HomeCN.

[0064]FIGS. 8 and 9 illustrate two separate versions of an RLAN made inaccordance with the teachings of the present invention wherein the RANIP Gateway is configured with a control signal port for establishing alimited direct connection with its Home UMTS Core Network. Inparticular, the limited connectivity transports information needed toprovide AAA function support for the CN.

[0065] The RAN IP Gateway control signal port may be configured, asillustrated in FIG. 8, to provide control signal data usingradius/diameter based access in which case the core network includes anInter Working Unit (IWU) as specified in 3GPP which converts AAAfunction information into conventional Mobile Application Part (MAP)signaling for connection with the HSS/HLR of the Core Network.Alternatively, as illustrated in FIG. 9, the RAN IP Gateway controlsignal port can be configured as a subset of a standard Gr interfacewhich supports MAP signaling which can be directly used by the HSS/HLRof the CN.

[0066] Preferably, the RAN IP Gateway employs a standard GI interfacewith the Internet and can be utilized as a stand-alone system withoutany association with a Core Network of a UMTS. However, in order tosupport mobility management with roaming and hand-over servicesavailable for subscriber UEs of the RLAN, an AAA function connectionwith a Core Network, such as by way of the various alternativesillustrated in FIGS. 7, 8, and 9, is desirable. In such case, inaddition to a standard GI interface between the RAN IP Gateway of theRLAN and the Internet, a mobile IP protocol is supported. Preferredexamples of such mobile IP protocols are the Mobile IP v4 protocol andthe Mobile IP v6 protocol as specified by IETF.

[0067]FIG. 10 illustrates IP packet data flow for a communicationbetween a first UE having a wireless connection with the RLAN and asecond UE outside the wireless service region of the RLAN where MobileIP v4 is implemented on the GI interface between the RAN IP Gateway andthe Internet. In such case, user data from the first UE is sent in IPpacket format from the RAN IP Gateway of the RLAN through the Internetto the address provided by the second UE. The second UE communicationsare directed to the Home Address of the first UE which is maintained atthe Core Network since in this example the first UE has the CN as itsHome CN. The CN receives the IP data packets from the second UE and thenthe CN forwards the IP packets to the current location of the first UEwhich is maintained in the CN's HLR as the Forwarding Address (FA) ofthe first UE.

[0068] In this example, since the first UE is “home”, the CN tunnels theIP Packets through the Internet to the RAN IP gateway for communicationto the first UE. In the case of the first UE traveling outside of theRLAN, its location will be registered with the Core Network and the datapackets directed to the address where the first UE is currently locatedbe used by the core network to direct the IP packet data to the currentlocation of the first UE.

[0069]Figure 10B illustrates an alternate approach where Mobile IP v4 isimplemented on the GI interface using with reverse path tunneling suchthat the RLAN directs the IP packets of the first UE's user data to theHome CN where they are relayed to the second UE in a conventionalmanner.

[0070] When the RLAN has connectivity using a GI interface thatimplements Mobile IP v6, the IP packet data exchange between the firstUE and the second UE will contain binding updates, as illustrated inFIG. 11A, which will reflect any redirection of the IP packets neededfor hand-over. FIG. 11B illustrates an alternative approach using a GIinterface implementing mobile IP v6 that includes tunneling between theRLAN and the Home CN. In such cases the CN directly tracks locationinformation of the first UE and the second UE may communicate with thefirst UE's Home CN in any type of conventional manner.

[0071] With reference to FIG. 12, there is shown the construction ofpreferred interfaces between the components of the RLAN of the presentinvention. The UE interface between the RLAN via the base station, NodeB, is preferably a standard Uu interface for connection with UEs asspecified by 3GPP. An Iub interface between each Node B and RNC ispreferably implemented both in the control plane and the user data planeas a layered stacked protocol having Internet Protocol (IP) as thetransport layer. Similarly at least a subset of an Iu-PS interface ispreferably provided between an RNC and the RAN IP Gateway that is alayered stacked protocol having IP as the transport layer.

[0072] In a conventional UMTS where SS7 is implemented over ATM, theMTP3/SSCF/SSCOP layers help SCCP, which is the top layer of the SS7stack, to plug onto an underlying ATM stack. In the preferred IPapproach used in conjunction with the present invention, the M3UA/SCTPstack helps SCCP connect onto IP. Essentially, the M3UA/SCTP stack inthe preferred IP-based configuration replaces the MTP3/SSCF/SSCOP layersthat are used in the conventional SS7-over-ATM approach. The specificdetails of these standard protocol stack architecture are defined in theIETF (Internet) standards. The use of IP in lieu of ATS enablescost-savings as well as PICO cells for office and campus departments.

[0073] Where the RLAN has multiple RNCs, the RNCs can be interfaced viaan Iur interface having layered stacked protocols for both the signalingplane and user plane using an IP transport layer. Each RNC is connectedto one or more Node Bs which in turn serve in plurality of UEs withinrespective geographic areas that may overlap to enable intra-RLANservice region handover.

[0074] Handover of a UE communication with one Node B within the RLAN toanother Node B within the RLAN, intra-RLAN handover, is conducted in theconventional manner specified in 3GPP for intra-UTRAN handover. However,when a UE communicating with a Node B of the RLAN moves outside the RLANservice region, handover is implemented via the RAN IP gateway utilizingIP packet service, preferably, implemented with Mobile IP v4 or MobileIP v6 as discussed above.

[0075]FIG. 13 illustrates the subcomponents of a preferred RLAN inaccordance with the present invention. The RNC can be divided intostandard Control and Serving Radio Network Subsystems (C-RNSs andS-RNSs) connected by an internal Iur interface. In such a configuration,the S-RNS functions are coupled to a SGSN subcomponent of the RAN IPgateway which supports a subset of the standard SGSN functions, namely,GPRS Mobility Management (GMM), Session Management (SM) and ShortMessage Service (SMS). The SGSN subcomponent interfaces with a GGSNsubcomponent having a subset of a standard GGSN functions including anaccess router and gateway functions support for the SGNS subcomponentfunctions and a GI interface with mobile IP for external connectivity tothe Internet. The SGSN subcomponent interface with the GGSN subcomponentis preferably via modified Gn/Gp interface, being a subset of thestandard Gn/Gp interface for a CN's SGNS and GGSN.

[0076] Optionally, the RAN IP Gateway has an AAA function communicationsubcomponent that is also connected to the SGSN subcomponent andprovides a port for limited external connectivity to an associated CN.The port supporting either a Gr interface or a Radius/Diameter interfaceas discussed above in connection with FIGS. 8 and 9.

[0077] Multiple RNCs of the RLAN can be provided coupled with the SGSNsubcomponent by an Iu-PS interface which includes sufficientconnectivity to support the functions of the SGSN subcomponent. Wheremultiple RNCs are provided, they are preferably coupled by a standardIur interface which utilizes an IP transport layer.

[0078] The use of IP for the transport layer of the various componentsof the RLAN readily lends itself to implementing the RNC functions inseparate computer servers to independently process the user data ofcommunications and the signaling as illustrated in FIG. 15. Referring toFIG. 16, there is a component diagram where the radio control means isdivided between U-plane and C-plane servers. In addition to the basicRLAN components, an optional Voice Gateway is also illustrated in FIGS.15 and 16.

[0079] Each Node B of the RLAN has a connection using an IP transportlayer with a U-plane server which transports user data. Each Node B ofthe RLAN also has a separate connection with a C-plane server via astandard Iub signal control interface having an IP transport layer. Boththe U-plane server and C-plane server are connected to the IP gatewayusing layered stacked protocols, preferably having IP as the transportlayer.

[0080] For multiple C-plane server configurations, each can be coupledto each other via a standard Iur interface, but only one is required tobe directly connected to the RIP GW. This allows the sharing ofresources for control signal processing which is useful when one area ofthe RLAN becomes much busier in other areas to spread out the signalprocessing between C-plane servers. A plurality of C-plane and U-planeservers can be connected in a mesh network for sharing both C-plane andU-plane resources via stacked layer protocols preferably having an IPtransport layer.

[0081] Where the optional voice gateway having external connectivity viaPCM circuit is provided, the U-plane server and C-plane server arecoupled to the voice gateway via a stacked layer protocols preferablyhaving an IP transport layer. The C-plane server is then coupled to theU-plane server via a Media gateway control protocol gateway (Megaco)over an IP transport layer. Megaco is a control plane protocol that setsup the bearer connection(s) between a Voice gateway elements, as part ofcall establishment.

[0082] Referring to FIGS. 17 and 18, there are shown, respectively,preferred C-plane and U-plane protocol stacks which are implementedbetween the Node Bs, RNCs (or U- and C-plane servers) and the RAN IPGateway of the RLAN. In each drawing, the preferred over air protocolstack implemented via the Uu interface with UEs is also shown.

[0083] The RLAN can be configured with voice support over its externalIP connection. In such case, the RIP gateway is connected with anInternet Service Provider (ISP) which in turn has a PCM voice gateway.The PCM voice gateway converts voice compression data into a Pulse CodeModulation (PCM) format for external voice communications.

[0084] Vocoders are provided that use Coder/Decoders (CODECs) forcompression of voice data. Two common types vocoder formats are the AMRvocoder format and G.729 compression format. FIGS. 19 and 21 showpreferred U-plane protocol stacks which are implemented where the voicegateway of the ISP to which the RLAN is connected uses the same type ofvoice compression interface as the UE. AMR vocoder format beingillustrated in FIG. 19; G.729 vocoder format being illustrated in FIG.21. The voice over IP is simply transferred as regular packet data overthe IP interface without change.

[0085] Where the UE utilizes a different voice compression protocol thanthe voice gateway of the ISP, a converter is provided in the RNC or theRAN IP Gateway. FIG. 20 shows preferred U-plane protocol stacks, wherethe UE utilizes an AMR vocoder and the ISP voice gateway utilizes aG.729 vocoder. Preferably, the RAN IP Gateway (RIP GW) includes theAMR/G.729 converter. In the case illustrated in FIG. 20, the converterconverts AMR compressed data received from the node B to G.729 formatcompressed voice format for output by the RIP GW. Where the RLANutilizes separate U-plane and C-plane servers, the compressed voice datais transported by a U-plane server and the converters may be located ineither the U-plane servers or the IP gateway.

[0086] With reference from FIGS. 22, there is shown preferred controlplane protocol stack architecture for supporting voice using standardH.323 format for a Session Initiated Protocol (H.323/SIP) over TCP/UDPcarry by IP. The control signaling is essentially the same irrespectiveof the type of voice data compression conducted in the U-Place.

[0087] Although the present invention has been described based onparticular configurations, other variations will be apparent to those ofordinary skill in the art and are within the scope of the presentinvention.

What is claimed is:
 1. A radio local area network (RLAN) for providingconcurrent wireless telecommunication services for a plurality of userequipments (UEs) between UEs and/or the Internet comprising: a firstbase station having a transceiver for conducting time division duplex(TDD) code division multiple access (CDMA) wireless communications withUEs in a selected geographic region; a first Radio Network Controller(RNC) coupled with said first base station for controlling base stationcommunication; and a Radio Access Network Internet Protocol (RAN IP)Gateway having a Gateway General Packet Radio Service (GPRS) SupportNode (GGSN) for connection with the Internet; and said Radio AccessNetwork Internet Protocol (RAN IP) Gateway coupled with said RNC via anIu-PS interface using a stacked, layered protocol connection having alower transport layer configured to use Internet Protocol (IP).
 2. Aradio local area network (RLAN) according to claim 1 wherein: said RNCis coupled with said first base station using a stacked, layeredprotocol connection having a lower transport layer configured to useInternet Protocol (IP).
 3. A RLAN according to claim 2 furthercomprising: a Voice Gateway having a Pulse Code Modulation (PCM) portfor external connection; and said Voice Gateway being coupled with saidfirst RNC using a stacked, layered protocol connections having a lowertransport layer configured to use Internet Protocol (IP).
 4. A RLANaccording to claim 2 comprising: a plurality of base stations, eachhaving a transceiver configured with a Uu interface for conducting timedivision duplex (TDD) wideband code division multiple access (W-CDMA)wireless communications with UEs in a selected geographic region; saidfirst RNC being coupled with said base stations using a stacked, layeredprotocol connection having a lower transport layer configured to useInternet Protocol (IP).
 5. A RLAN according to claim 2 furthercomprising: a second RNC coupled with a second base station using astacked, layered protocol connection having a lower transport layerconfigured to use Internet Protocol (IP); and said first RNC beingcoupled with said second RNC using a stacked, layered protocolconnection having a lower transport layer configured to use InternetProtocol (IP).
 6. A RLAN according to claim 5 wherein said RAN IPGateway has a Serving GPRS Support Node (SGSN) that is coupled with saidRNCs.
 7. A RLAN according to claim 5 wherein said RAN IP Gateway has aServing GPRS Support Node (SGSN) that is coupled with said first RNC. 8.A RLAN according to claim 1 wherein said RAN IP Gateway has a ServingGPRS Support Node (SGSN) that is coupled with said first RNC.
 9. A RLANaccording to claim 1 comprising: a plurality of base stations that eachhave a transceiver for conducting time division duplex (TDD) codedivision multiple access (CDMA) wireless communications with UEs in aselected geographic region; and a plurality of RNCs that are eachcoupled with a group of base stations of said plurality of base stationsusing a stacked, layered protocol connection having a lower transportlayer configured to use Internet Protocol (IP); and said RAN IP Gatewayhas a Serving GPRS Support Node (SGSN) that is coupled with saidplurality of RNCs using a stacked, layered protocol connection having alower transport layer configured to use Internet Protocol (IP).
 10. ARLAN according to claim 9 wherein said RNCs are coupled with each otherusing a stacked, layered protocol connection having a lower transportlayer configured to use Internet Protocol (IP).